Method and apparatus for video coding

ABSTRACT

Aspects of the disclosure provide methods and apparatuses for video encoding/decoding. In some examples, an apparatus for video decoding includes processing circuitry. The processing circuitry can receive coded information of pictures in a coded video sequence. The coded information can include a coding tree unit (CTU) size information that indicates a CTU size selected for the pictures. The CTU size information can be encoded using a truncated unary code. The processing circuitry can determine the selected CTU size based on the CTU size information encoded using the truncated unary code. The processing circuitry can reconstruct samples in the pictures based on the selected CTU size. The selected CTU size can be 32×32, 64×64, or 128×128 luma samples.

INCORPORATION BY REFERENCE

This present disclosure claims the benefit of priority to U.S. Provisional Application No. 62/886,056, “Improved SPS Header Syntax and Descriptor for CTU Size” filed on Aug. 13, 2019, which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present disclosure describes embodiments generally related to video coding.

BACKGROUND

The background description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent the work is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

Video coding and decoding can be performed using inter-picture prediction with motion compensation. Uncompressed digital video can include a series of pictures, each picture having a spatial dimension of, for example, 1920×1080 luminance samples and associated chrominance samples. The series of pictures can have a fixed or variable picture rate (informally also known as frame rate), of, for example 60 pictures per second or 60 Hz. Uncompressed video has specific bitrate requirements. For example, 1080p60 4:2:0 video at 8 bit per sample (1920×1080 luminance sample resolution at 60 Hz frame rate) requires close to 1.5 Gbit/s bandwidth. An hour of such video requires more than 600 GBytes of storage space.

One purpose of video coding and decoding can be the reduction of redundancy in the input video signal, through compression. Compression can help reduce the aforementioned bandwidth and/or storage space requirements, in some cases by two orders of magnitude or more. Both lossless compression and lossy compression, as well as a combination thereof can be employed. Lossless compression refers to techniques where an exact copy of the original signal can be reconstructed from the compressed original signal. When using lossy compression, the reconstructed signal may not be identical to the original signal, but the distortion between original and reconstructed signals is small enough to make the reconstructed signal useful for the intended application. In the case of video, lossy compression is widely employed. The amount of distortion tolerated depends on the application; for example, users of certain consumer streaming applications may tolerate higher distortion than users of television distribution applications. The compression ratio achievable can reflect that: higher allowable/tolerable distortion can yield higher compression ratios.

A video encoder and decoder can utilize techniques from several broad categories, including, for example, motion compensation, transform, quantization, and entropy coding.

Video codec technologies can include techniques known as intra coding. In intra coding, sample values are represented without reference to samples or other data from previously reconstructed reference pictures. In some video codecs, the picture is spatially subdivided into blocks of samples. When all blocks of samples are coded in intra mode, that picture can be an intra picture. Intra pictures and their derivations such as independent decoder refresh pictures, can be used to reset the decoder state and can, therefore, be used as the first picture in a coded video bitstream and a video session, or as a still image. The samples of an intra block can be exposed to a transform, and the transform coefficients can be quantized before entropy coding. Intra prediction can be a technique that minimizes sample values in the pre-transform domain. In some cases, the smaller the DC value after a transform is, and the smaller the AC coefficients are, the fewer the bits that are required at a given quantization step size to represent the block after entropy coding.

Traditional intra coding such as known from, for example MPEG-2 generation coding technologies, does not use intra prediction. However, some newer video compression technologies include techniques that attempt, from, for example, surrounding sample data and/or metadata obtained during the encoding/decoding of spatially neighboring, and preceding in decoding order, blocks of data. Such techniques are henceforth called “intra prediction” techniques. Note that in at least some cases, intra prediction is using reference data only from the current picture under reconstruction and not from reference pictures.

There can be many different forms of intra prediction. When more than one of such techniques can be used in a given video coding technology, the technique in use can be coded in an intra prediction mode. In certain cases, modes can have submodes and/or parameters, and those can be coded individually or included in the mode codeword. Which codeword to use for a given mode/submode/parameter combination can have an impact in the coding efficiency gain through intra prediction, and so can the entropy coding technology used to translate the codewords into a bitstream.

A certain mode of intra prediction was introduced with H.264, refined in H.265, and further refined in newer coding technologies such as joint exploration model (JEM), versatile video coding (VVC), and benchmark set (BMS). A predictor block can be formed using neighboring sample values belonging to already available samples. Sample values of neighboring samples are copied into the predictor block according to a direction. A reference to the direction in use can be coded in the bitstream or may itself be predicted.

Referring to FIG. 1A, depicted in the lower right is a subset of nine predictor directions known from H.265's 33 possible predictor directions (corresponding to the 33 angular modes of the 35 intra modes). The point where the arrows converge (101) represents the sample being predicted. The arrows represent the direction from which the sample is being predicted. For example, arrow (102) indicates that sample (101) is predicted from a sample or samples to the upper right, at a 45 degree angle from the horizontal. Similarly, arrow (103) indicates that sample (101) is predicted from a sample or samples to the lower left of sample (101), in a 22.5 degree angle from the horizontal.

Still referring to FIG. 1A, on the top left there is depicted a square block (104) of 4×4 samples (indicated by a dashed, boldface line). The square block (104) includes 16 samples, each labelled with an “S”, its position in the Y dimension (e.g., row index) and its position in the X dimension (e.g., column index). For example, sample S21 is the second sample in the Y dimension (from the top) and the first (from the left) sample in the X dimension. Similarly, sample S44 is the fourth sample in block (104) in both the Y and X dimensions. As the block is 4×4 samples in size, S44 is at the bottom right. Further shown are reference samples that follow a similar numbering scheme. A reference sample is labelled with an R, its Y position (e.g., row index) and X position (column index) relative to block (104). In both H.264 and H.265, prediction samples neighbor the block under reconstruction; therefore no negative values need to be used.

Intra picture prediction can work by copying reference sample values from the neighboring samples as appropriated by the signaled prediction direction. For example, assume the coded video bitstream includes signaling that, for this block, indicates a prediction direction consistent with arrow (102)—that is, samples are predicted from a prediction sample or samples to the upper right, at a 45 degree angle from the horizontal. In that case, samples S41, S32, S23, and S14 are predicted from the same reference sample R05. Sample S44 is then predicted from reference sample R08.

In certain cases, the values of multiple reference samples may be combined, for example through interpolation, in order to calculate a reference sample; especially when the directions are not evenly divisible by 45 degrees.

The number of possible directions has increased as video coding technology has developed. In H.264 (year 2003), nine different directions could be represented. That increased to 33 in H.265 (year 2013), and JEM/VVC/BMS, at the time of disclosure, can support up to 65 directions. Experiments have been conducted to identify the most likely directions, and certain techniques in the entropy coding are used to represent those likely directions in a small number of bits, accepting a certain penalty for less likely directions. Further, the directions themselves can sometimes be predicted from neighboring directions used in neighboring, already decoded, blocks.

FIG. 1B shows a schematic (180) that depicts 65 intra prediction directions according to JEM to illustrate the increasing number of prediction directions over time.

The mapping of intra prediction directions bits in the coded video bitstream that represent the direction can be different from video coding technology to video coding technology; and can range, for example, from simple direct mappings of prediction direction to intra prediction mode, to codewords, to complex adaptive schemes involving most probable modes, and similar techniques. In all cases, however, there can be certain directions that are statistically less likely to occur in video content than certain other directions. As the goal of video compression is the reduction of redundancy, those less likely directions will, in a well working video coding technology, be represented by a larger number of bits than more likely directions.

Motion compensation can be a lossy compression technique and can relate to techniques where a block of sample data from a previously reconstructed picture or part thereof (reference picture), after being spatially shifted in a direction indicated by a motion vector (MV henceforth), is used for the prediction of a newly reconstructed picture or picture part. In some cases, the reference picture can be the same as the picture currently under reconstruction. MVs can have two dimensions X and Y, or three dimensions, the third being an indication of the reference picture in use (the latter, indirectly, can be a time dimension).

In some video compression techniques, an MV applicable to a certain area of sample data can be predicted from other MVs, for example from those related to another area of sample data spatially adjacent to the area under reconstruction, and preceding that MV in decoding order. Doing so can substantially reduce the amount of data required for coding the MV, thereby removing redundancy and increasing compression. MV prediction can work effectively, for example, because when coding an input video signal derived from a camera (known as natural video) there is a statistical likelihood that areas larger than the area to which a single MV is applicable move in a similar direction and, therefore, can in some cases be predicted using a similar motion vector derived from MVs of neighboring area. That results in the MV found for a given area to be similar or the same as the MV predicted from the surrounding MVs, and that in turn can be represented, after entropy coding, in a smaller number of bits than what would be used if coding the MV directly. In some cases, MV prediction can be an example of lossless compression of a signal (namely: the MVs) derived from the original signal (namely: the sample stream). In other cases, MV prediction itself can be lossy, for example because of rounding errors when calculating a predictor from several surrounding MVs.

Various MV prediction mechanisms are described in H.265/HEVC (ITU-T Rec. H.265, “High Efficiency Video Coding”, December 2016). Out of the many MV prediction mechanisms that H.265 offers, described here is a technique henceforth referred to as “spatial merge”.

Referring to FIG. 2, a current block (201) comprises samples that have been found by the encoder during the motion search process to be predictable from a previous block of the same size that has been spatially shifted. Instead of coding that MV directly, the MV can be derived from metadata associated with one or more reference pictures, for example from the most recent (in decoding order) reference picture, using the MV associated with either one of five surrounding samples, denoted A0, A1, and B0, B1, B2 (202 through 206, respectively). In H.265, the MV prediction can use predictors from the same reference picture that the neighboring block is using.

SUMMARY

Aspects of the disclosure provide methods and apparatuses for video encoding/decoding. In some examples, an apparatus for video decoding includes processing circuitry. The processing circuitry can receive coded information of pictures in a coded video sequence. The coded information can include a coding tree unit (CTU) size information that indicates a CTU size selected for the pictures. The CTU size information can be encoded using a truncated unary code. The processing circuitry can determine the selected CTU size based on the CTU size information encoded using the truncated unary code and reconstruct samples in the pictures based on the selected CTU size. In an embodiment, the selected CTU size is 32×32, 64×64, or 128×128 luma samples.

In an embodiment, the processing circuitry can determine, based on the CTU size information encoded using the truncated unary code, a coded value from a bit string in the coded information where a maximum number of bits in the bit string is 2. The coded value can be 0, 1, and 2 when the bit string is 0, 10, and 11, respectively. The processing circuitry can determine the selected CTU size based on the coded value.

In an example, the processing circuitry can determine that the selected CTU size is 128, 64, and 32 in a case that the coded value is 0, 1, and 2, respectively. The processing circuitry can determine the selected CTU size to be 2^(CtbLog2SizeY) where a value of CtbLog 2SizeY is a difference between 7 and the coded value.

In an example, the processing circuitry can determine that the selected CTU size is 32, 64, and 128 in a case that the coded value is 0, 1, and 2, respectively. The processing circuitry can determine the selected CTU size to be 2^(CtbLog2SizeY) where a value of CtbLog 2SizeY is a sum of the coded value and 5.

In an embodiment, the coded information is in a sequence parameter set header for the coded video sequence.

Aspects of the disclosure also provide a non-transitory computer-readable medium storing instructions which when executed by a computer for video decoding cause the computer to perform any of the methods for video decoding.

BRIEF DESCRIPTION OF THE DRAWINGS

Further features, the nature, and various advantages of the disclosed subject matter will be more apparent from the following detailed description and the accompanying drawings in which:

FIG. 1A is a schematic illustration of an exemplary subset of intra prediction modes.

FIG. 1B is an illustration of exemplary intra prediction directions.

FIG. 2 is a schematic illustration of a current block and its surrounding spatial merge candidates in one example.

FIG. 3 is a schematic illustration of a simplified block diagram of a communication system (300) in accordance with an embodiment.

FIG. 4 is a schematic illustration of a simplified block diagram of a communication system (400) in accordance with an embodiment.

FIG. 5 is a schematic illustration of a simplified block diagram of a decoder in accordance with an embodiment.

FIG. 6 is a schematic illustration of a simplified block diagram of an encoder in accordance with an embodiment.

FIG. 7 shows a block diagram of an encoder in accordance with another embodiment.

FIG. 8 shows a block diagram of a decoder in accordance with another embodiment.

FIGS. 9A-9B show a coding tree unit (CTU) and a quadtree plus binary tree (QTBT) structure according to embodiments of the disclosure.

FIG. 10A shows an example of a syntax and a corresponding descriptor in an Sequence Parameter Setting (SPS) header according to an embodiment of the disclosure.

FIG. 10B shows an example of unsigned integer Exp-Golomb coding according to an embodiment of the disclosure.

FIG. 11A shows an example of a syntax and a corresponding descriptor in an SPS header according to an embodiment of the disclosure.

FIG. 11B shows an example of a fixed-length coding using 2 bits according to an embodiment of the disclosure.

FIG. 12A shows an example of a syntax and a corresponding descriptor in an SPS header according to an embodiment of the disclosure.

FIG. 12B shows an example of truncated unary coding according to an embodiment of the disclosure.

FIG. 13 shows a flow chart outlining a process (1300) according to an embodiment of the disclosure.

FIG. 14 is a schematic illustration of a computer system in accordance with an embodiment.

DETAILED DESCRIPTION OF EMBODIMENTS

FIG. 3 illustrates a simplified block diagram of a communication system (300) according to an embodiment of the present disclosure. The communication system (300) includes a plurality of terminal devices that can communicate with each other, via, for example, a network (350). For example, the communication system (300) includes a first pair of terminal devices (310) and (320) interconnected via the network (350). In the FIG. 3 example, the first pair of terminal devices (310) and (320) performs unidirectional transmission of data. For example, the terminal device (310) may code video data (e.g., a stream of video pictures that are captured by the terminal device (310)) for transmission to the other terminal device (320) via the network (350). The encoded video data can be transmitted in the form of one or more coded video bitstreams. The terminal device (320) may receive the coded video data from the network (350), decode the coded video data to recover the video pictures and display video pictures according to the recovered video data. Unidirectional data transmission may be common in media serving applications and the like.

In another example, the communication system (300) includes a second pair of terminal devices (330) and (340) that performs bidirectional transmission of coded video data that may occur, for example, during videoconferencing. For bidirectional transmission of data, in an example, each terminal device of the terminal devices (330) and (340) may code video data (e.g., a stream of video pictures that are captured by the terminal device) for transmission to the other terminal device of the terminal devices (330) and (340) via the network (350). Each terminal device of the terminal devices (330) and (340) also may receive the coded video data transmitted by the other terminal device of the terminal devices (330) and (340), and may decode the coded video data to recover the video pictures and may display video pictures at an accessible display device according to the recovered video data.

In the FIG. 3 example, the terminal devices (310), (320), (330) and (340) may be illustrated as servers, personal computers and smart phones but the principles of the present disclosure may be not so limited. Embodiments of the present disclosure find application with laptop computers, tablet computers, media players and/or dedicated video conferencing equipment. The network (350) represents any number of networks that convey coded video data among the terminal devices (310), (320), (330) and (340), including for example wireline (wired) and/or wireless communication networks. The communication network (350) may exchange data in circuit-switched and/or packet-switched channels. Representative networks include telecommunications networks, local area networks, wide area networks and/or the Internet. For the purposes of the present discussion, the architecture and topology of the network (350) may be immaterial to the operation of the present disclosure unless explained herein below.

FIG. 4 illustrates, as an example for an application for the disclosed subject matter, the placement of a video encoder and a video decoder in a streaming environment. The disclosed subject matter can be equally applicable to other video enabled applications, including, for example, video conferencing, digital TV, storing of compressed video on digital media including CD, DVD, memory stick and the like, and so on.

A streaming system may include a capture subsystem (413), that can include a video source (401), for example a digital camera, creating for example a stream of video pictures (402) that are uncompressed. In an example, the stream of video pictures (402) includes samples that are taken by the digital camera. The stream of video pictures (402), depicted as a bold line to emphasize a high data volume when compared to encoded video data (404) (or coded video bitstreams), can be processed by an electronic device (420) that includes a video encoder (403) coupled to the video source (401). The video encoder (403) can include hardware, software, or a combination thereof to enable or implement aspects of the disclosed subject matter as described in more detail below. The encoded video data (404) (or encoded video bitstream (404)), depicted as a thin line to emphasize the lower data volume when compared to the stream of video pictures (402), can be stored on a streaming server (405) for future use. One or more streaming client subsystems, such as client subsystems (406) and (408) in FIG. 4 can access the streaming server (405) to retrieve copies (407) and (409) of the encoded video data (404). A client subsystem (406) can include a video decoder (410), for example, in an electronic device (430). The video decoder (410) decodes the incoming copy (407) of the encoded video data and creates an outgoing stream of video pictures (411) that can be rendered on a display (412) (e.g., display screen) or other rendering device (not depicted). In some streaming systems, the encoded video data (404), (407), and (409) (e.g., video bitstreams) can be encoded according to certain video coding/compression standards. Examples of those standards include ITU-T Recommendation H.265. In an example, a video coding standard under development is informally known as Versatile Video Coding (VVC). The disclosed subject matter may be used in the context of VVC.

It is noted that the electronic devices (420) and (430) can include other components (not shown). For example, the electronic device (420) can include a video decoder (not shown) and the electronic device (430) can include a video encoder (not shown) as well.

FIG. 5 shows a block diagram of a video decoder (510) according to an embodiment of the present disclosure. The video decoder (510) can be included in an electronic device (530). The electronic device (530) can include a receiver (531) (e.g., receiving circuitry). The video decoder (510) can be used in the place of the video decoder (410) in the FIG. 4 example.

The receiver (531) may receive one or more coded video sequences to be decoded by the video decoder (510); in the same or another embodiment, one coded video sequence at a time, where the decoding of each coded video sequence is independent from other coded video sequences. The coded video sequence may be received from a channel (501), which may be a hardware/software link to a storage device which stores the encoded video data. The receiver (531) may receive the encoded video data with other data, for example, coded audio data and/or ancillary data streams, that may be forwarded to their respective using entities (not depicted). The receiver (531) may separate the coded video sequence from the other data. To combat network jitter, a buffer memory (515) may be coupled in between the receiver (531) and an entropy decoder/parser (520) (“parser (520)” henceforth). In certain applications, the buffer memory (515) is part of the video decoder (510). In others, it can be outside of the video decoder (510) (not depicted). In still others, there can be a buffer memory (not depicted) outside of the video decoder (510), for example to combat network jitter, and in addition another buffer memory (515) inside the video decoder (510), for example to handle playout timing. When the receiver (531) is receiving data from a store/forward device of sufficient bandwidth and controllability, or from an isosynchronous network, the buffer memory (515) may not be needed, or can be small. For use on best effort packet networks such as the Internet, the buffer memory (515) may be required, can be comparatively large and can be advantageously of adaptive size, and may at least partially be implemented in an operating system or similar elements (not depicted) outside of the video decoder (510).

The video decoder (510) may include the parser (520) to reconstruct symbols (521) from the coded video sequence. Categories of those symbols include information used to manage operation of the video decoder (510), and potentially information to control a rendering device such as a render device (512) (e.g., a display screen) that is not an integral part of the electronic device (530) but can be coupled to the electronic device (530), as was shown in FIG. 5. The control information for the rendering device(s) may be in the form of Supplemental Enhancement Information (SEI messages) or Video Usability Information (VUI) parameter set fragments (not depicted). The parser (520) may parse/entropy-decode the coded video sequence that is received. The coding of the coded video sequence can be in accordance with a video coding technology or standard, and can follow various principles, including variable length coding, Huffman coding, arithmetic coding with or without context sensitivity, and so forth. The parser (520) may extract from the coded video sequence, a set of subgroup parameters for at least one of the subgroups of pixels in the video decoder, based upon at least one parameter corresponding to the group. Subgroups can include Groups of Pictures (GOPs), pictures, tiles, slices, macroblocks, Coding Units (CUs), blocks, Transform Units (TUs), Prediction Units (PUs) and so forth. The parser (520) may also extract from the coded video sequence information such as transform coefficients, quantizer parameter values, motion vectors, and so forth.

The parser (520) may perform an entropy decoding/parsing operation on the video sequence received from the buffer memory (515), so as to create symbols (521).

Reconstruction of the symbols (521) can involve multiple different units depending on the type of the coded video picture or parts thereof (such as: inter and intra picture, inter and intra block), and other factors. Which units are involved, and how, can be controlled by the subgroup control information that was parsed from the coded video sequence by the parser (520). The flow of such subgroup control information between the parser (520) and the multiple units below is not depicted for clarity.

Beyond the functional blocks already mentioned, the video decoder (510) can be conceptually subdivided into a number of functional units as described below. In a practical implementation operating under commercial constraints, many of these units interact closely with each other and can, at least partly, be integrated into each other. However, for the purpose of describing the disclosed subject matter, the conceptual subdivision into the functional units below is appropriate.

A first unit is the scaler/inverse transform unit (551). The scaler/inverse transform unit (551) receives a quantized transform coefficient as well as control information, including which transform to use, block size, quantization factor, quantization scaling matrices, etc. as symbol(s) (521) from the parser (520). The scaler/inverse transform unit (551) can output blocks comprising sample values, that can be input into aggregator (555).

In some cases, the output samples of the scaler/inverse transform (551) can pertain to an intra coded block; that is: a block that is not using predictive information from previously reconstructed pictures, but can use predictive information from previously reconstructed parts of the current picture. Such predictive information can be provided by an intra picture prediction unit (552). In some cases, the intra picture prediction unit (552) generates a block of the same size and shape of the block under reconstruction, using surrounding already reconstructed information fetched from the current picture buffer (558). The current picture buffer (558) buffers, for example, partly reconstructed current picture and/or fully reconstructed current picture. The aggregator (555), in some cases, adds, on a per sample basis, the prediction information the intra prediction unit (552) has generated to the output sample information as provided by the scaler/inverse transform unit (551).

In other cases, the output samples of the scaler/inverse transform unit (551) can pertain to an inter coded, and potentially motion compensated block. In such a case, a motion compensation prediction unit (553) can access reference picture memory (557) to fetch samples used for prediction. After motion compensating the fetched samples in accordance with the symbols (521) pertaining to the block, these samples can be added by the aggregator (555) to the output of the scaler/inverse transform unit (551) (in this case called the residual samples or residual signal) so as to generate output sample information. The addresses within the reference picture memory (557) from where the motion compensation prediction unit (553) fetches prediction samples can be controlled by motion vectors, available to the motion compensation prediction unit (553) in the form of symbols (521) that can have, for example X, Y, and reference picture components. Motion compensation also can include interpolation of sample values as fetched from the reference picture memory (557) when sub-sample exact motion vectors are in use, motion vector prediction mechanisms, and so forth.

The output samples of the aggregator (555) can be subject to various loop filtering techniques in the loop filter unit (556). Video compression technologies can include in-loop filter technologies that are controlled by parameters included in the coded video sequence (also referred to as coded video bitstream) and made available to the loop filter unit (556) as symbols (521) from the parser (520), but can also be responsive to meta-information obtained during the decoding of previous (in decoding order) parts of the coded picture or coded video sequence, as well as responsive to previously reconstructed and loop-filtered sample values.

The output of the loop filter unit (556) can be a sample stream that can be output to the render device (512) as well as stored in the reference picture memory (557) for use in future inter-picture prediction.

Certain coded pictures, once fully reconstructed, can be used as reference pictures for future prediction. For example, once a coded picture corresponding to a current picture is fully reconstructed and the coded picture has been identified as a reference picture (by, for example, the parser (520)), the current picture buffer (558) can become a part of the reference picture memory (557), and a fresh current picture buffer can be reallocated before commencing the reconstruction of the following coded picture.

The video decoder (510) may perform decoding operations according to a predetermined video compression technology in a standard, such as ITU-T Rec. H.265. The coded video sequence may conform to a syntax specified by the video compression technology or standard being used, in the sense that the coded video sequence adheres to both the syntax of the video compression technology or standard and the profiles as documented in the video compression technology or standard. Specifically, a profile can select certain tools as the only tools available for use under that profile from all the tools available in the video compression technology or standard. Also necessary for compliance can be that the complexity of the coded video sequence is within bounds as defined by the level of the video compression technology or standard. In some cases, levels restrict the maximum picture size, maximum frame rate, maximum reconstruction sample rate (measured in, for example megasamples per second), maximum reference picture size, and so on. Limits set by levels can, in some cases, be further restricted through Hypothetical Reference Decoder (HRD) specifications and metadata for HRD buffer management signaled in the coded video sequence.

In an embodiment, the receiver (531) may receive additional (redundant) data with the encoded video. The additional data may be included as part of the coded video sequence(s). The additional data may be used by the video decoder (510) to properly decode the data and/or to more accurately reconstruct the original video data. Additional data can be in the form of, for example, temporal, spatial, or signal noise ratio (SNR) enhancement layers, redundant slices, redundant pictures, forward error correction codes, and so on.

FIG. 6 shows a block diagram of a video encoder (603) according to an embodiment of the present disclosure. The video encoder (603) is included in an electronic device (620). The electronic device (620) includes a transmitter (640) (e.g., transmitting circuitry). The video encoder (603) can be used in the place of the video encoder (403) in the FIG. 4 example.

The video encoder (603) may receive video samples from a video source (601) (that is not part of the electronic device (620) in the FIG. 6 example) that may capture video image(s) to be coded by the video encoder (603). In another example, the video source (601) is a part of the electronic device (620).

The video source (601) may provide the source video sequence to be coded by the video encoder (603) in the form of a digital video sample stream that can be of any suitable bit depth (for example: 8 bit, 10 bit, 12 bit, . . . ), any colorspace (for example, BT.601 Y CrCB, RGB, . . . ), and any suitable sampling structure (for example Y CrCb 4:2:0, Y CrCb 4:4:4). In a media serving system, the video source (601) may be a storage device storing previously prepared video. In a videoconferencing system, the video source (601) may be a camera that captures local image information as a video sequence. Video data may be provided as a plurality of individual pictures that impart motion when viewed in sequence. The pictures themselves may be organized as a spatial array of pixels, wherein each pixel can comprise one or more samples depending on the sampling structure, color space, etc. in use. A person skilled in the art can readily understand the relationship between pixels and samples. The description below focuses on samples.

According to an embodiment, the video encoder (603) may code and compress the pictures of the source video sequence into a coded video sequence (643) in real time or under any other time constraints as required by the application. Enforcing appropriate coding speed is one function of a controller (650). In some embodiments, the controller (650) controls other functional units as described below and is functionally coupled to the other functional units. The coupling is not depicted for clarity. Parameters set by the controller (650) can include rate control related parameters (picture skip, quantizer, lambda value of rate-distortion optimization techniques, . . . ), picture size, group of pictures (GOP) layout, maximum motion vector search range, and so forth. The controller (650) can be configured to have other suitable functions that pertain to the video encoder (603) optimized for a certain system design.

In some embodiments, the video encoder (603) is configured to operate in a coding loop. As an oversimplified description, in an example, the coding loop can include a source coder (630) (e.g., responsible for creating symbols, such as a symbol stream, based on an input picture to be coded, and a reference picture(s)), and a (local) decoder (633) embedded in the video encoder (603). The decoder (633) reconstructs the symbols to create the sample data in a similar manner as a (remote) decoder also would create (as any compression between symbols and coded video bitstream is lossless in the video compression technologies considered in the disclosed subject matter). The reconstructed sample stream (sample data) is input to the reference picture memory (634). As the decoding of a symbol stream leads to bit-exact results independent of decoder location (local or remote), the content in the reference picture memory (634) is also bit exact between the local encoder and remote encoder. In other words, the prediction part of an encoder “sees” as reference picture samples exactly the same sample values as a decoder would “see” when using prediction during decoding. This fundamental principle of reference picture synchronicity (and resulting drift, if synchronicity cannot be maintained, for example because of channel errors) is used in some related arts as well.

The operation of the “local” decoder (633) can be the same as of a “remote” decoder, such as the video decoder (510), which has already been described in detail above in conjunction with FIG. 5. Briefly referring also to FIG. 5, however, as symbols are available and encoding/decoding of symbols to a coded video sequence by an entropy coder (645) and the parser (520) can be lossless, the entropy decoding parts of the video decoder (510), including the buffer memory (515), and parser (520) may not be fully implemented in the local decoder (633).

An observation that can be made at this point is that any decoder technology except the parsing/entropy decoding that is present in a decoder also necessarily needs to be present, in substantially identical functional form, in a corresponding encoder. For this reason, the disclosed subject matter focuses on decoder operation. The description of encoder technologies can be abbreviated as they are the inverse of the comprehensively described decoder technologies. Only in certain areas a more detail description is required and provided below.

During operation, in some examples, the source coder (630) may perform motion compensated predictive coding, which codes an input picture predictively with reference to one or more previously coded picture from the video sequence that were designated as “reference pictures.” In this manner, the coding engine (632) codes differences between pixel blocks of an input picture and pixel blocks of reference picture(s) that may be selected as prediction reference(s) to the input picture.

The local video decoder (633) may decode coded video data of pictures that may be designated as reference pictures, based on symbols created by the source coder (630). Operations of the coding engine (632) may advantageously be lossy processes. When the coded video data may be decoded at a video decoder (not shown in FIG. 6), the reconstructed video sequence typically may be a replica of the source video sequence with some errors. The local video decoder (633) replicates decoding processes that may be performed by the video decoder on reference pictures and may cause reconstructed reference pictures to be stored in the reference picture cache (634). In this manner, the video encoder (603) may store copies of reconstructed reference pictures locally that have common content as the reconstructed reference pictures that will be obtained by a far-end video decoder (absent transmission errors).

The predictor (635) may perform prediction searches for the coding engine (632). That is, for a new picture to be coded, the predictor (635) may search the reference picture memory (634) for sample data (as candidate reference pixel blocks) or certain metadata such as reference picture motion vectors, block shapes, and so on, that may serve as an appropriate prediction reference for the new pictures. The predictor (635) may operate on a sample block-by-pixel block basis to find appropriate prediction references. In some cases, as determined by search results obtained by the predictor (635), an input picture may have prediction references drawn from multiple reference pictures stored in the reference picture memory (634).

The controller (650) may manage coding operations of the source coder (630), including, for example, setting of parameters and subgroup parameters used for encoding the video data.

Output of all aforementioned functional units may be subjected to entropy coding in the entropy coder (645). The entropy coder (645) translates the symbols as generated by the various functional units into a coded video sequence, by lossless compressing the symbols according to technologies such as Huffman coding, variable length coding, arithmetic coding, and so forth.

The transmitter (640) may buffer the coded video sequence(s) as created by the entropy coder (645) to prepare for transmission via a communication channel (660), which may be a hardware/software link to a storage device which would store the encoded video data. The transmitter (640) may merge coded video data from the video coder (603) with other data to be transmitted, for example, coded audio data and/or ancillary data streams (sources not shown).

The controller (650) may manage operation of the video encoder (603). During coding, the controller (650) may assign to each coded picture a certain coded picture type, which may affect the coding techniques that may be applied to the respective picture. For example, pictures often may be assigned as one of the following picture types:

An Intra Picture (I picture) may be one that may be coded and decoded without using any other picture in the sequence as a source of prediction. Some video codecs allow for different types of intra pictures, including, for example Independent Decoder Refresh (“IDR”) Pictures. A person skilled in the art is aware of those variants of I pictures and their respective applications and features.

A predictive picture (P picture) may be one that may be coded and decoded using intra prediction or inter prediction using at most one motion vector and reference index to predict the sample values of each block.

A bi-directionally predictive picture (B Picture) may be one that may be coded and decoded using intra prediction or inter prediction using at most two motion vectors and reference indices to predict the sample values of each block. Similarly, multiple-predictive pictures can use more than two reference pictures and associated metadata for the reconstruction of a single block.

Source pictures commonly may be subdivided spatially into a plurality of sample blocks (for example, blocks of 4×4, 8×8, 4×8, or 16×16 samples each) and coded on a block-by-block basis. Blocks may be coded predictively with reference to other (already coded) blocks as determined by the coding assignment applied to the blocks' respective pictures. For example, blocks of I pictures may be coded non-predictively or they may be coded predictively with reference to already coded blocks of the same picture (spatial prediction or intra prediction). Pixel blocks of P pictures may be coded predictively, via spatial prediction or via temporal prediction with reference to one previously coded reference picture. Blocks of B pictures may be coded predictively, via spatial prediction or via temporal prediction with reference to one or two previously coded reference pictures.

The video encoder (603) may perform coding operations according to a predetermined video coding technology or standard, such as ITU-T Rec. H.265. In its operation, the video encoder (603) may perform various compression operations, including predictive coding operations that exploit temporal and spatial redundancies in the input video sequence. The coded video data, therefore, may conform to a syntax specified by the video coding technology or standard being used.

In an embodiment, the transmitter (640) may transmit additional data with the encoded video. The source coder (630) may include such data as part of the coded video sequence. Additional data may comprise temporal/spatial/SNR enhancement layers, other forms of redundant data such as redundant pictures and slices, SEI messages, VUI parameter set fragments, and so on.

A video may be captured as a plurality of source pictures (video pictures) in a temporal sequence. Intra-picture prediction (often abbreviated to intra prediction) makes use of spatial correlation in a given picture, and inter-picture prediction makes uses of the (temporal or other) correlation between the pictures. In an example, a specific picture under encoding/decoding, which is referred to as a current picture, is partitioned into blocks. When a block in the current picture is similar to a reference block in a previously coded and still buffered reference picture in the video, the block in the current picture can be coded by a vector that is referred to as a motion vector. The motion vector points to the reference block in the reference picture, and can have a third dimension identifying the reference picture, in case multiple reference pictures are in use.

In some embodiments, a bi-prediction technique can be used in the inter-picture prediction. According to the bi-prediction technique, two reference pictures, such as a first reference picture and a second reference picture that are both prior in decoding order to the current picture in the video (but may be in the past and future, respectively, in display order) are used. A block in the current picture can be coded by a first motion vector that points to a first reference block in the first reference picture, and a second motion vector that points to a second reference block in the second reference picture. The block can be predicted by a combination of the first reference block and the second reference block.

Further, a merge mode technique can be used in the inter-picture prediction to improve coding efficiency.

According to some embodiments of the disclosure, predictions, such as inter-picture predictions and intra-picture predictions are performed in the unit of blocks. For example, according to the HEVC standard, a picture in a sequence of video pictures is partitioned into coding tree units (CTU) for compression, the CTUs in a picture have the same size, such as 64×64 pixels, 32×32 pixels, or 16×16 pixels. In general, a CTU includes three coding tree blocks (CTBs), which are one luma CTB and two chroma CTBs. Each CTU can be recursively quadtree split into one or multiple coding units (CUs). For example, a CTU of 64×64 pixels can be split into one CU of 64×64 pixels, or 4 CUs of 32×32 pixels, or 16 CUs of 16×16 pixels. In an example, each CU is analyzed to determine a prediction type for the CU, such as an inter prediction type or an intra prediction type. The CU is split into one or more prediction units (PUs) depending on the temporal and/or spatial predictability. Generally, each PU includes a luma prediction block (PB), and two chroma PBs. In an embodiment, a prediction operation in coding (encoding/decoding) is performed in the unit of a prediction block. Using a luma prediction block as an example of a prediction block, the prediction block includes a matrix of values (e.g., luma values) for pixels, such as 8×8 pixels, 16×16 pixels, 8×16 pixels, 16×8 pixels, and the like.

FIG. 7 shows a diagram of a video encoder (703) according to another embodiment of the disclosure. The video encoder (703) is configured to receive a processing block (e.g., a prediction block) of sample values within a current video picture in a sequence of video pictures, and encode the processing block into a coded picture that is part of a coded video sequence. In an example, the video encoder (703) is used in the place of the video encoder (403) in the FIG. 4 example.

In an HEVC example, the video encoder (703) receives a matrix of sample values for a processing block, such as a prediction block of 8×8 samples, and the like. The video encoder (703) determines whether the processing block is best coded using intra mode, inter mode, or bi-prediction mode using, for example, rate-distortion optimization. When the processing block is to be coded in intra mode, the video encoder (703) may use an intra prediction technique to encode the processing block into the coded picture; and when the processing block is to be coded in inter mode or bi-prediction mode, the video encoder (703) may use an inter prediction or bi-prediction technique, respectively, to encode the processing block into the coded picture. In certain video coding technologies, merge mode can be an inter picture prediction submode where the motion vector is derived from one or more motion vector predictors without the benefit of a coded motion vector component outside the predictors. In certain other video coding technologies, a motion vector component applicable to the subject block may be present. In an example, the video encoder (703) includes other components, such as a mode decision module (not shown) to determine the mode of the processing blocks.

In the FIG. 7 example, the video encoder (703) includes the inter encoder (730), an intra encoder (722), a residue calculator (723), a switch (726), a residue encoder (724), a general controller (721), and an entropy encoder (725) coupled together as shown in FIG. 7.

The inter encoder (730) is configured to receive the samples of the current block (e.g., a processing block), compare the block to one or more reference blocks in reference pictures (e.g., blocks in previous pictures and later pictures), generate inter prediction information (e.g., description of redundant information according to inter encoding technique, motion vectors, merge mode information), and calculate inter prediction results (e.g., predicted block) based on the inter prediction information using any suitable technique. In some examples, the reference pictures are decoded reference pictures that are decoded based on the encoded video information.

The intra encoder (722) is configured to receive the samples of the current block (e.g., a processing block), in some cases compare the block to blocks already coded in the same picture, generate quantized coefficients after transform, and in some cases also intra prediction information (e.g., an intra prediction direction information according to one or more intra encoding techniques). In an example, the intra encoder (722) also calculates intra prediction results (e.g., predicted block) based on the intra prediction information and reference blocks in the same picture.

The general controller (721) is configured to determine general control data and control other components of the video encoder (703) based on the general control data. In an example, the general controller (721) determines the mode of the block, and provides a control signal to the switch (726) based on the mode. For example, when the mode is the intra mode, the general controller (721) controls the switch (726) to select the intra mode result for use by the residue calculator (723), and controls the entropy encoder (725) to select the intra prediction information and include the intra prediction information in the bitstream; and when the mode is the inter mode, the general controller (721) controls the switch (726) to select the inter prediction result for use by the residue calculator (723), and controls the entropy encoder (725) to select the inter prediction information and include the inter prediction information in the bitstream.

The residue calculator (723) is configured to calculate a difference (residue data) between the received block and prediction results selected from the intra encoder (722) or the inter encoder (730). The residue encoder (724) is configured to operate based on the residue data to encode the residue data to generate the transform coefficients. In an example, the residue encoder (724) is configured to convert the residue data from a spatial domain to a frequency domain, and generate the transform coefficients. The transform coefficients are then subject to quantization processing to obtain quantized transform coefficients. In various embodiments, the video encoder (703) also includes a residue decoder (728). The residue decoder (728) is configured to perform inverse-transform, and generate the decoded residue data. The decoded residue data can be suitably used by the intra encoder (722) and the inter encoder (730). For example, the inter encoder (730) can generate decoded blocks based on the decoded residue data and inter prediction information, and the intra encoder (722) can generate decoded blocks based on the decoded residue data and the intra prediction information. The decoded blocks are suitably processed to generate decoded pictures and the decoded pictures can be buffered in a memory circuit (not shown) and used as reference pictures in some examples.

The entropy encoder (725) is configured to format the bitstream to include the encoded block. The entropy encoder (725) is configured to include various information according to a suitable standard, such as the HEVC standard. In an example, the entropy encoder (725) is configured to include the general control data, the selected prediction information (e.g., intra prediction information or inter prediction information), the residue information, and other suitable information in the bitstream. Note that, according to the disclosed subject matter, when coding a block in the merge submode of either inter mode or bi-prediction mode, there is no residue information.

FIG. 8 shows a diagram of a video decoder (810) according to another embodiment of the disclosure. The video decoder (810) is configured to receive coded pictures that are part of a coded video sequence, and decode the coded pictures to generate reconstructed pictures. In an example, the video decoder (810) is used in the place of the video decoder (410) in the FIG. 4 example.

In the FIG. 8 example, the video decoder (810) includes an entropy decoder (871), an inter decoder (880), a residue decoder (873), a reconstruction module (874), and an intra decoder (872) coupled together as shown in FIG. 8.

The entropy decoder (871) can be configured to reconstruct, from the coded picture, certain symbols that represent the syntax elements of which the coded picture is made up. Such symbols can include, for example, the mode in which a block is coded (such as, for example, intra mode, inter mode, bi-predicted mode, the latter two in merge submode or another submode), prediction information (such as, for example, intra prediction information or inter prediction information) that can identify certain sample or metadata that is used for prediction by the intra decoder (872) or the inter decoder (880), respectively, residual information in the form of, for example, quantized transform coefficients, and the like. In an example, when the prediction mode is inter or bi-predicted mode, the inter prediction information is provided to the inter decoder (880); and when the prediction type is the intra prediction type, the intra prediction information is provided to the intra decoder (872). The residual information can be subject to inverse quantization and is provided to the residue decoder (873).

The inter decoder (880) is configured to receive the inter prediction information, and generate inter prediction results based on the inter prediction information.

The intra decoder (872) is configured to receive the intra prediction information, and generate prediction results based on the intra prediction information.

The residue decoder (873) is configured to perform inverse quantization to extract de-quantized transform coefficients, and process the de-quantized transform coefficients to convert the residual from the frequency domain to the spatial domain. The residue decoder (873) may also require certain control information (to include the Quantizer Parameter (QP)), and that information may be provided by the entropy decoder (871) (data path not depicted as this may be low volume control information only).

The reconstruction module (874) is configured to combine, in the spatial domain, the residual as output by the residue decoder (873) and the prediction results (as output by the inter or intra prediction modules as the case may be) to form a reconstructed block, that may be part of the reconstructed picture, which in turn may be part of the reconstructed video. It is noted that other suitable operations, such as a deblocking operation and the like, can be performed to improve the visual quality.

It is noted that the video encoders (403), (603), and (703), and the video decoders (410), (510), and (810) can be implemented using any suitable technique. In an embodiment, the video encoders (403), (603), and (703), and the video decoders (410), (510), and (810) can be implemented using one or more integrated circuits. In another embodiment, the video encoders (403), (603), and (603), and the video decoders (410), (510), and (810) can be implemented using one or more processors that execute software instructions.

A block partitioning structure can be referred to as a coding tree. In some embodiments, the block partitioning structure uses a quad-tree (QT) plus binary tree (BT). For example, by using a QT structure, a CTU is split into CUs to adapt to various local characteristics. A decision on whether to code a picture area using an inter-picture (temporal) or intra-picture (spatial) prediction can be made at a CU level. Each CU can be further split into one, two, or four PUs according to a PU splitting type. Inside one PU, a same prediction process is applied and relevant information can be transmitted to a decoder on a PU basis.

After obtaining a residual block by applying a prediction process based on the PU splitting type, a CU can be partitioned into TUs according to another QT structure. As can be seen, there are multiple partition conceptions including CU, PU, and TU.

At a picture boundary, in some embodiments, implicit quadtree split can be employed so that a block will keep QT splitting until the size fits the picture boundary.

In some embodiments, a quadtree plus binary tree (QTBT) structure is employed. The QTBT structure removes the concepts of multiple partition types (e.g., the CU, PU, and TU concepts), and supports more flexibility for CU partition shapes. In the QTBT block structure, a CU can have either a square or rectangular shape.

FIG. 9A shows a CTU (910) that is partitioned by using a QTBT structure (920) shown in FIG. 9B. The CTU (910) is first partitioned by a QT structure. The QT leaf nodes are further partitioned by a BT structure or a QT structure. There can be two splitting types, symmetric horizontal splitting and symmetric vertical splitting, in the BT splitting. The BT leaf nodes are called CUs that can be used for prediction and transform processing without any further partitioning. Accordingly, CU, PU, and TU have the same block size in the QTBT coding block structure.

In some embodiments, a CU can include coding blocks (CBs) of different color components. For example, one CU contains one luma CB and two chroma CBs in the case of P and B slices of the 4:2:0 chroma format. A CU can include a CB of a single color component. For example, one CU contains only one luma CB or just two chroma CBs in the case of I slices.

The following parameters are defined for the QTBT partitioning scheme in some embodiments:

-   -   CTU size: root node size of a quadtree, e.g., such as in HEVC.     -   MinQTSize: minimum allowed QT leaf node size.     -   MaxBTSize: maximum allowed BT root node size.     -   MaxBTDepth: maximum allowed BT depth.     -   MinBTSize: minimum allowed BT leaf node size.

In one example of the QTBT partitioning structure, the CTU size is set as 128×128 luma samples with two corresponding 64×64 blocks of chroma samples, the MinQTSize is set as 16×16, the MaxBTSize is set as 64×64, the MinBTSize (for both width and height) is set as 4×4, and the MaxBTDepth is set as 4. The QT partitioning is applied to the CTU first to generate QT leaf nodes. The QT leaf nodes may have a size from 16×16 (i.e., the MinQTSize) to 128×128 (i.e., the CTU size). If the leaf QT node is 128×128, it will not be further split by the binary tree since the size exceeds the MaxBTSize (i.e., 64×64). Otherwise, the leaf QT node could be further partitioned by the binary tree. Therefore, the QT leaf node is also the root node for the binary tree and it has the BT depth as 0.

When the BT depth reaches MaxBTDepth (i.e., 4), no further splitting is considered. When the BT node has a width equal to MinBTSize (i.e., 4), no further horizontal splitting is considered. Similarly, when the BT node has height equal to MinBTSize, no further vertical splitting is considered. The leaf nodes of the binary tree are further processed by prediction and transform processing without any further partitioning. In an embodiment, a maximum CTU size is 256×256 luma samples.

In FIGS. 9A and 9B, the solid lines indicate QT splitting and dotted lines indicate BT splitting. In each splitting (i.e., non-leaf) node of the binary tree, one flag can be signaled to indicate which splitting type (i.e., horizontal or vertical) is used. For example, 0 indicates a horizontal splitting and 1 indicates a vertical splitting. For the QT splitting, there is no need to indicate the splitting type since quadtree splitting always splits a block both horizontally and vertically to produce 4 sub-blocks with an equal size.

In some embodiments, the QTBT scheme supports the flexibility for the luma and chroma to have a separate QTBT structure. For example, for P and B slices, the luma and chroma blocks in one CTU share the same QTBT structure. However, for I slices, the luma CTB is partitioned into CUs by a QTBT structure, and the chroma blocks are partitioned into chroma CUs by another QTBT structure. Thus, a CU in an I slice can include, or consist of, a coding block of the luma component or coding blocks of two chroma components, and a CU in a P or B slice can include, or consist of, coding blocks of all three color components.

In some embodiments, inter prediction for small blocks is restricted to reduce memory access of motion compensation. For example, bi-prediction is not supported for 4×8 and 8×4 blocks, and inter prediction is not supported for 4×4 blocks. In some examples, such as when the QTBT is implemented, the above restrictions can be removed.

A CTU size can be represented by a width (or a height) M of a CTU. In an embodiment, when the CTU has a square shape, the CTU size can also be represented by M×M luma samples in the CTU. Thus, the CTU size can be referred to as M or M×M. In an embodiment, a same CTU size can be used to code (e.g., encode/decode) pictures in a video sequence, and coding information indicating the CTU size can be signaled in a Sequence Parameter Setting (SPS) (e.g., in a SPS header) and shared among the pictures in the video sequence.

In some embodiments, a plurality of CTU sizes (e.g., four CTU sizes), such as 16, 32, 64, and 128, can be used. Thus, the four CTU sizes can be 16×16, 32×32, 64×64, and 128×128 luma samples, respectively. A varible ‘CtbSizeY’ can be used to represent the four CTU sizes (e.g., 16, 32, 64, and 128). Numbers 4-7 are the base 2 logarithms of the four CTU sizes 16, 32, 64, and 128, respectively, and can be represented by a variable ‘CtbLog 2SizeY’. Four numbers 2, 3, 4, and 5 can be used to code 16 (or 16×16 luma samples), 32 (or 32×32 luma samples), 64 (or 64×64 luma samples), and 128 (or 128×128 luma samples), respectively, and can be represented by a variable ‘log 2_ctu_size_minus2’. For example, the four numbers 2-5 (or log 2_ctu_size_minus2) are differences between the base 2 logarithms (or CtbLog 2SizeY) of the four CTU sizes 16, 32, 64, and 128 and a value 2, respectively. An example of a SPS header syntax for CTU sizes can be set to ‘log 2_ctu_size_minus2’ as shown in FIG. 10A.

The four numbers 2-5 (or log 2_ctu_size_minus2) can be coded using an entropy coding tool, for example Exp-Golomb coding, such as unsigned integer 0-th order Exp-Golomb coding (or ue(v)). Thus, a corresponding descriptor for the variable log 2_ctu_size_minus2 is ue(v) in FIG. 10A.

FIG. 10B shows an example of ue(v) coding according to an embodiment of the disclosure. Variable bit strings (1010) can be used to code the variable log 2_ctu_size_minus2 (also referred to coded values or code numbers (codeNums)) (1020). For example, the bit strings 011, 00100, 00101, and 00110 are used to code the codeNums 2-5, respectively.

Based on the description above, semantics for CTU sizes can be described below. log 2_ctu_size_minus2 plus 2 specifies a luma CTB size of each CTU (as shown in Eq. (1)). log 2_min_luma_coding_block_size_minus2 plus 2 specifies a minimum luma coding block size.

The variables CtbLog 2SizeY and CtbSizeY can be derived using Eqs. (1)-(2).

Ctb Log 2SizeY=log 2_ctu_size_minus2+2  Eq. (1)

CtbSizeY=1<<Ctb Log 2SizeY  Eq. (2)

For example, the bit string 011 represents the codeNum 2 based on ue(v) coding as shown in FIG. 10B. Thus, a value of the variable log 2_ctu_size_minus2 is 2. A value of the variable CtbLog 2SizeY is determined to be 4 based on Eq. (1). A value of the variable CtbSizeY is determined to be 2^(CtbLog2SizeY) based on Eq. (2), and thus the value of the variable CtbSizeY is 2⁴=16. Thus, the CTU size is 16 or 16×16 luma samples. The above description can be applied to other bit strings that indicate various CTU sizes, such as 32, 64, or 128.

In some examples, a much larger overhead can occur when using the CTU size 16 instead of using larger CTU sizes (e.g., 128). Thus, a decoding time can be longer when using the CTU size 16. In an example, a CTU size of 16×16 luma samples corresponds to an 8×8 chroma CTB size. For certain coding modules, processing the 8×8 chroma CTB size is challenging because a loop filter typically uses a 16×16 block as an input. Further, the CTU size 16×16 can cause a significant encoding loss. Thus, the CTU size 16 can be removed.

In some embodiments, a plurality of CTU sizes (e.g., three CTU sizes), such as 32, 64, and 128 (or 32×32, 64×64, 128×128 luma samples) are used. Similarly, the varible ‘CtbSizeY’ can be used to represent the three CTU sizes. Numbers 5-7 are the base 2 logarithms of the three CTU sizes 32, 64, and 128, respectively, and can be represented by the variable ‘CtbLog 2SizeY’. Syntax and corresponding description in the SPE header can be modified as below and shown in FIG. 11A.

Three numbers 0-2 can be used to code the three CTU sizes, e.g., 32 (or 32×32 luma samples), 64 (or 64×64 luma samples), and 128 (or 128×128 luma samples), respectively, and can be represented by a variable ‘log 2_ctu_size_minus5’. For example, the three numbers 0-2 (or log 2_ctu_size_minus5) are differences between the base 2 logarithms (i.e., 5-7) (or CtbLog 2SizeY) of the three CTU sizes 32, 64, and 128 and a number 5, respectively. As described above, a SPS header syntax for CTU sizes can be set to log 2_ctu_size_minus5′ as shown in FIG. 11A.

The three numbers 0-2 (or log 2_ctu_size_minus5) can be coded using an entropy coding tool having a fixed length coding, such as unsigned integer using n bits (or u(n)). In an example, 2 bits can be used (e.g., n=2). Thus, a corresponding descriptor is u(2) in FIG. 11A. Comparing FIGS. 10A and 11A, the differences are indicated by labels 1110 and 1120.

FIG. 11B shows an example of u(2) coding according to an embodiment of the disclosure. Fixed-length bit strings (1130) can be used to code the variable log 2_ctu_size_minus5 (also referred to coded values or codeNums) (1140). For example, the bit strings 00, 01, and 10 can be used to code the codeNums 0-2, respectively.

Semantics for CTU sizes are described as follows, and some differences associated with log 2_ctu_size_minus2 and log 2_ctu_size_minus5 are highlighted using italics.

log 2_ctu_size_minus5 plus 5 specifies the luma CTB size of each CTU. In an example, it is a requirement of bitstream conformance that the value of log 2_ctu_size_minus5 be less than or equal to 2.

log 2_min_luma_coding_block_size_minus2 plus 2 can specify the minimum luma coding block size.

The variables CtbLog 2SizeY and CtbSizeY can be derived using Eqs. (2)-(3) where Eq. (3) is different from Eq. (1).

Ctb Log 2SizeY=log 2_ctu_size_minus5+5  Eq. (3)

For example, the bit string 00 represents the codeNum 0 based on u(2) coding as shown in FIG. 11B. Thus, log 2_ctu_size_minus5 is 0. A value of the variable CtbLog 2SizeY is determined to be 5 based on Eq. (3). A value of the variable CtbSizeY is determined to be 2^(CtbLog2SizeY) based on Eq. (2), and thus the value of the variable CtbSizeY is 2⁵=32. Thus, the CTU size is 32 or 32×32 luma samples. The above description can be applied to other bit strings that indicates other CTU sizes (e.g., 64 or 128).

In some embodiments, only three numbers (e.g., the codeNums 0-2) representing the three CTU sizes are encoded. Using the fixed length coding u(2) to describe the syntax log 2_ctu_size_minus5 can waste one bit, for example, when the encoded number is 0 or 1.

In some embodiments described above, the number 0 (e.g., the codeNum 0) can be used to represent the CTU size 32 (or 32×32 luma samples) and the number 2 (e.g., the codeNum 2) can be used to represent the CTU size 128 (or 128×128 luma samples). In various examples, the CTU size 128 is the most frequently used CTU size in a video sequence, and thus encoding the CTU size 128 with the number 2 can decrease coding efficiency and increase coding complexity.

In some embodiments, for pictures in a video sequence, a CTU size to be used for coding the pictures can be indicated in coded information for the video sequence. Information indicating the CTU size can be in an SPS header. The CTU size can be one of a plurality of CTU sizes, such as the three CTU sizes 32, 64, and 128. According to aspects of the disclosure, a truncated unary coding can be used to code (e.g., encode/decode) numbers (e.g., coded values or codeNums) indicating CTU sizes. When compared with the fixed-length coding described in above (e.g., with reference to FIGS. 11A-11B), the truncated unary coding can improve coding efficiency, for example, by eliminating unnecessary waste of bits. Thus, a size of the SPS header can be smaller when the truncated unary coding is used instead of the fixed-length coding u(2), and thus improving the coding efficiency. Further, in some examples, an illegal bitstream generated by a non-conforming encoder (e.g., enabling the CTU size 16×16 that is not allowed in some standards or coders) can be avoided.

In an embodiment, the three CTU sizes 32, 64, and 128 (or 32×32, 64×64, 128×128 luma samples) can be used. As described above, the variable ‘CtbSizeY’ can be used to represent the three CTU sizes. Numbers 5-7 are the base 2 logarithms of the three CTU sizes 32, 64, and 128, respectively, and can be represented by the variable ‘CtbLog 2SizeY’. Syntax and corresponding description in the SPS header can be modified as below and shown in FIG. 12A.

The three numbers 0-2 can be used to code or represent the three CTU sizes. According to aspects of the disclosure, 0 is used to represent (or code) 128 (or 128×128 luma samples), 1 is used to represent (or code) 64 (or 64×64 luma samples), and 2 is used to represent (or code) 32 (or 32×32 luma samples), and thus the three numbers can be represented by a variable ‘seven_minus_log 2_ctu_size’. For example, the three numbers 0-2 (or seven_minus_log 2_ctu_size) are differences between 7 and the base 2 logarithms 7, 6, and 5 (or CtbLog 2SizeY) of the three CTU sizes 128, 64, and 32, respectively. As described above, a SPS header syntax for CTU sizes can be set to ‘seven_minus_log 2_ctu_size’ as shown in FIG. 12A.

The three numbers 0-2 (or seven_minus_log 2_ctu_size) can be coded using the truncated unary coding (or tu(v)) as shown by a descriptor is tu(v) in FIG. 12A. In an embodiment, the truncated unary coding is a unary coding that generates a bin string (or bit string) of ‘1’ followed by a ‘0’ when a number to be coded is less than a maximum value cMax. When the number to be coded is equal to the maximum value cMax, the last ‘0’ is truncated. In an embodiment, the maximum value cMax is 2 when coding the three numbers 0-2 (or seven_minus_log 2_ctu_size). FIG. 12B shows an example of the truncated unary coding according to an embodiment of the disclosure. Variable-length bit strings (1230) are used to code the variable seven_minus_log 2_ctu_size (also referred to coded values or codeNums (1240)). The bit string 0 can be used to code the codeNum 0. The bit string 10 can be used to code the codeNum 1. The bit string 11 can be used to code the codeNum 2. Comparing FIGS. 11A and 12A, the differences are indicated by labels (1210) and (1220). Comparing FIGS. 10A and 12A, the differences are indicated by the labels (1210) and (1220).

In general, the three numbers 0-2 (or seven_minus_log 2_ctu_size) can be coded using any suitable coding method, such as variable-length coding (e.g., the truncated unary coding, Exp-Golomb coding), fixed-length coding (e.g., u(n)), or the like where the number 0 represents the CTU size 128. Code numbers can be assigned based on frequency of use of the CTU size. For example, a CTU size of 128 can be assigned to a lowest or smaller code number.

As described above in FIGS. 12A-12B, the variable ‘seven_minus_log 2_ctu_size’ can be used to describe CTU sizes, and the CTU size 128 can be coded with the coded value or the codeNum 0. Further, the bit string 0 having 1 bit can be used to code the codeNum 0. In various examples, when the CTU size 128 is used more frequently than other CTU sizes (e.g., 32 and 64), coding the CTU size 128 with 1 bit can improve coding efficiency. For example, the bit string 00110 can be used to indicate the CTU size 128 has 5 bits (FIG. 10B) or the bit string 10 can used to indicate the CTU size 128 has 2 bits (FIG. 11B).

Semantics for CTU sizes are described as follows, and some differences between seven_minus_log 2_ctu_size and other variable(s) (log 2_ctu_size_minus5 and log 2_ctu_size_minus2) are highlighted using italics.

seven_minus_log 2_ctu_size specifies the luma CTB size of each CTU. In an example, it is a requirement of bitstream conformance that the value of seven_minus_log 2_ctu_size be less than or equal to 2.

log 2_min_luma_coding_block_size_minus2 plus 2 can specify the minimum luma coding block size.

The variables CtbLog 2SizeY and CtbSizeY can be derived using Eqs. (2) and (4).

Ctb Log 2SizeY=7−seven_minus_log 2_ctu_size  Eq. (4)

Referring to FIG. 12B, for example, the bit string 0 can be used to represent the codeNum 0 based on tu(v) coding having the maximum value cMax of 2. Thus, a value of the variable seven_minus_log 2_ctu_size is 0. A value of the variable CtbLog 2SizeY is determined to be 7 based on Eq. (4). A value of the variable CtbSizeY is determined to be 2^(CtbLog2SizeY) based on Eq. (2), and thus the value of the variable CtbSizeY is 2⁷=128. Thus, the CTU size is 128 or 128×128 luma samples. The above description can be applied to other bit strings that indicate other CTU sizes (e.g., 32 or 64).

According to aspects of the disclosure, the coded information of the pictures in the coded video sequence can be received by a decoder. The coded information can indicate a CTU size that is selected or used to encode the pictures, for example, by an encoder. The selected CTU size can be one of a plurality of CTU sizes, such as the three CTU sizes 32, 64, and 128. The coded information can be encoded/decoded using the truncated unary coding to obtain the selected CTU size. In an example, the coding information can indicate a coding tool (e.g., the truncated unary coding) used to code the CTU size. In another example, the coding tool is predetermined or signaled beforehand.

In an embodiment, the coded information is in an SPS header (e.g., a syntax and a descriptor of the SPS header), such as described above with reference to FIGS. 12A-12B. The coded information can include a bit string (e.g., the bit string 10 in FIG. 12B). In an example, a coded value/codeNum (e.g., a seven_minus_log 2_ctu_size) can be determined from the bit string using the truncated unary coding and the coded value is the number 1 shown in FIG. 12B. In an example, the maximum value cMax used in the truncated unary coding is 2. Further, the selected CTU size (e.g., 64) can be determined from the coded value (e.g., the number 1) based on the syntax and associated semantics (e.g., Eq. (4) and Eq. (2)). For example, a value of the variable CtbLog 2SizeY is determined to be a difference between 7 and the coded value using Eq. (4), and thus the value of the variable CtbLog 2SizeY is 7 when seven_minus_log 2_ctu_size is 0. Then a value of the variable CtbSizeY is determined to be 2^(CtbLog2SizeY) using Eq. (2), and thus the value of the variable CtbSizeY is 2⁷=128 when CtbLog 2SizeY is 7.

As described above with reference to FIGS. 12A-12B, coding a most frequently used CTU size with a smaller number of bits can improve coding efficiency. In some examples, the most frequently used CTU size is 128, and thus the CTU size 128 can be coded with 1 bit (e.g., the bit string ‘0’ as shown in FIG. 12B).

In some embodiments, a plurality of CTU sizes (e.g., three CTU sizes), such as 32, 64, and 128, can be represented using the variable log 2_ctu_size_minus5, for example, using Eqs. (2) and (3) and coded using truncated unary coding tu(v) having the maximum value cMax of 2, such as shown in FIG. 12B. In an example, the CTU size 128 is encoded with the coded value (or codeNum) 2, and thus the bit string 11 is used to encode the number 2 and the CTU size 128. In an example the CTU size 64 is encoded with the coded value (or codeNum) 1, and thus the bit string 10 is used to encode the number 1 and the CTU size 64. In an example, the CTU size 32 is encoded with the coded value (or codeNum) 0, and thus the bit string 0 is used to encode the number 0 and the CTU size 32. Thus, a coded value (or log 2_ctu_size_minus5) can be determined from a bit string using the truncated unary coding with the maximum value cMax of 2. Further, the selected CTU size can be determined from the coded value based on the syntax and associated semantics (e.g., Eq. (3) and Eq. (2)). For example, a value of the variable CtbLog 2SizeY can be determined to be a sum of 5 and the coded value using Eq. (3). Then a value of the variable CtbSizeY can be determined to be 2^(CtbLog2SizeY) using Eq. (2).

FIG. 13 shows a flow chart outlining a process (1300) according to an embodiment of the disclosure. The process (1300) can be used to determine a CTU size to be used for pictures in a coded video sequence. In various embodiments, the process (1300) are executed by processing circuitry, such as the processing circuitry in the terminal devices (310), (320), (330) and (340), the processing circuitry that performs functions of the video encoder (403), the processing circuitry that performs functions of the video decoder (410), the processing circuitry that performs functions of the video decoder (510), the processing circuitry that performs functions of the video encoder (603), and the like. In some embodiments, the process (1300) is implemented in software instructions, thus when the processing circuitry executes the software instructions, the processing circuitry performs the process (1300). The process starts at (S1301) and proceeds to (S1310).

At (S1310), coded information of the pictures in the coded video sequence can be received, for example, by a decoder. The coded information can include CTU size information that indicates a CTU size that is selected for the pictures, for example, by an encoder to encode the pictures. The selected CTU size can be one of a plurality of CTU sizes, such as the three CTU sizes 32×32, 64×64, and 128×128 luma samples. The plurality of CTU sizes can include any suitable number of CTU sizes and can include any suitable CTU size(s). The CTU size information can be encoded using the truncated unary code or other coding schemes.

In an example, the coded information indicates a coding tool used to code the selected CTU size. For example, the coding information is in an SPS header that indicates the coding tool (e.g., tu(v), u(2), or ue(v)). In some examples, the syntax is included in the SPS header, and thus indicating the corresponding semantics.

At (S1320), the selected CTU size can be determined using the coding tool (e.g., the truncated unary coding) based on the CTU size information. For example, the coded information is decoded using the truncated unary decoding, as described above with reference to FIGS. 12A-12B. In an embodiment, the CTU size information includes a bit string. A coded value (e.g., a codeNum) can be determined from the bit string using the truncated unary decoding. For example, the coded value can be determined to be 0, 1, and 2 when the bit string is 0, 10, and 11, respectively and a maximum value Cmax used in the truncated unary coding is 2. Further, the selected CTU size can be determined based on the coded value, for example, using the syntax (or the corresponding semantics) indicated in the coding information.

In an example, the syntax indicates that the coded value refers to a value of the variable seven_minus_log 2_ctu_size, and thus Eqs. (2) and (4) can be used to obtain the CTU size. Accordingly, the selected CTU size is 128 when the coded value is 0. The selected CTU size is 64 when the coded value is 1. The selected CTU size is 32 when the coded value is 2. Further, the selected CTU size can be determined to be 2^(CtbLog2SizeY) where a value of the variable CtbLog 2SizeY is a difference between 7 and the coded value.

In an example, the syntax indicates that the coded value refers to a value of the variable log 2_ctu_size_minus5, and thus Eqs. (2) and (3) can be used to obtain the selected CTU size. Accordingly, the selected CTU size is 128 when the coded value is 2. The selected CTU size is 64 when the coded value is 1. The selected CTU size is 32 when the coded value is 0. Further, the selected CTU size can be determined to be 2^(CtbLog2SizeY) where a value of the variable CtbLog 2SizeY is a sum of the coded value and 5.

At (S1330), samples in the pictures can be reconstructed based on the selected CTU size. For example, one of the pictures can be partitioned into CTUs having the selected CTU size. Each of the CTUs can be further partitioned into CUs where inter predictions and/or intra prediction can be used to reconstruct the samples in the CUs. The process (1300) proceeds to (S1399) and terminates.

The techniques described above, can be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media. For example, FIG. 14 shows a computer system (1400) suitable for implementing certain embodiments of the disclosed subject matter.

The computer software can be coded using any suitable machine code or computer language, that may be subject to assembly, compilation, linking, or like mechanisms to create code comprising instructions that can be executed directly, or through interpretation, micro-code execution, and the like, by one or more computer central processing units (CPUs), Graphics Processing Units (GPUs), and the like.

The instructions can be executed on various types of computers or components thereof, including, for example, personal computers, tablet computers, servers, smartphones, gaming devices, internet of things devices, and the like.

The components shown in FIG. 14 for computer system (1400) are exemplary in nature and are not intended to suggest any limitation as to the scope of use or functionality of the computer software implementing embodiments of the present disclosure. Neither should the configuration of components be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary embodiment of a computer system (1400).

Computer system (1400) may include certain human interface input devices. Such a human interface input device may be responsive to input by one or more human users through, for example, tactile input (such as: keystrokes, swipes, data glove movements), audio input (such as: voice, clapping), visual input (such as: gestures), olfactory input (not depicted). The human interface devices can also be used to capture certain media not necessarily directly related to conscious input by a human, such as audio (such as: speech, music, ambient sound), images (such as: scanned images, photographic images obtain from a still image camera), video (such as two-dimensional video, three-dimensional video including stereoscopic video).

Input human interface devices may include one or more of (only one of each depicted): keyboard (1401), mouse (1402), trackpad (1403), touch screen (1410), data-glove (not shown), joystick (1405), microphone (1406), scanner (1407), camera (1408).

Computer system (1400) may also include certain human interface output devices. Such human interface output devices may be stimulating the senses of one or more human users through, for example, tactile output, sound, light, and smell/taste. Such human interface output devices may include tactile output devices (for example tactile feedback by the touch-screen (1410), data-glove (not shown), or joystick (1405), but there can also be tactile feedback devices that do not serve as input devices), audio output devices (such as: speakers (1409), headphones (not depicted)), visual output devices (such as screens (1410) to include CRT screens, LCD screens, plasma screens, OLED screens, each with or without touch-screen input capability, each with or without tactile feedback capability—some of which may be capable to output two dimensional visual output or more than three dimensional output through means such as stereographic output; virtual-reality glasses (not depicted), holographic displays and smoke tanks (not depicted)), and printers (not depicted).

Computer system (1400) can also include human accessible storage devices and their associated media such as optical media including CD/DVD ROM/RW (1420) with CD/DVD or the like media (1421), thumb-drive (1422), removable hard drive or solid state drive (1423), legacy magnetic media such as tape and floppy disc (not depicted), specialized ROM/ASIC/PLD based devices such as security dongles (not depicted), and the like.

Those skilled in the art should also understand that term “computer readable media” as used in connection with the presently disclosed subject matter does not encompass transmission media, carrier waves, or other transitory signals.

Computer system (1400) can also include an interface to one or more communication networks. Networks can for example be wireless, wireline, optical. Networks can further be local, wide-area, metropolitan, vehicular and industrial, real-time, delay-tolerant, and so on. Examples of networks include local area networks such as Ethernet, wireless LANs, cellular networks to include GSM, 3G, 4G, 5G, LTE and the like, TV wireline or wireless wide area digital networks to include cable TV, satellite TV, and terrestrial broadcast TV, vehicular and industrial to include CANBus, and so forth. Certain networks commonly require external network interface adapters that attached to certain general purpose data ports or peripheral buses (1449) (such as, for example USB ports of the computer system (1400)); others are commonly integrated into the core of the computer system (1400) by attachment to a system bus as described below (for example Ethernet interface into a PC computer system or cellular network interface into a smartphone computer system). Using any of these networks, computer system (1400) can communicate with other entities. Such communication can be uni-directional, receive only (for example, broadcast TV), uni-directional send-only (for example CANbus to certain CANbus devices), or bi-directional, for example to other computer systems using local or wide area digital networks. Certain protocols and protocol stacks can be used on each of those networks and network interfaces as described above.

Aforementioned human interface devices, human-accessible storage devices, and network interfaces can be attached to a core (1440) of the computer system (1400).

The core (1440) can include one or more Central Processing Units (CPU) (1441), Graphics Processing Units (GPU) (1442), specialized programmable processing units in the form of Field Programmable Gate Areas (FPGA) (1443), hardware accelerators for certain tasks (1444), and so forth. These devices, along with Read-only memory (ROM) (1445), Random-access memory (1446), internal mass storage such as internal non-user accessible hard drives, SSDs, and the like (1447), may be connected through a system bus (1448). In some computer systems, the system bus (1448) can be accessible in the form of one or more physical plugs to enable extensions by additional CPUs, GPU, and the like. The peripheral devices can be attached either directly to the core's system bus (1448), or through a peripheral bus (1449). Architectures for a peripheral bus include PCI, USB, and the like.

CPUs (1441), GPUs (1442), FPGAs (1443), and accelerators (1444) can execute certain instructions that, in combination, can make up the aforementioned computer code. That computer code can be stored in ROM (1445) or RAM (1446). Transitional data can be also be stored in RAM (1446), whereas permanent data can be stored for example, in the internal mass storage (1447). Fast storage and retrieve to any of the memory devices can be enabled through the use of cache memory, that can be closely associated with one or more CPU (1441), GPU (1442), mass storage (1447), ROM (1445), RAM (1446), and the like.

The computer readable media can have computer code thereon for performing various computer-implemented operations. The media and computer code can be those specially designed and constructed for the purposes of the present disclosure, or they can be of the kind well known and available to those having skill in the computer software arts.

As an example and not by way of limitation, the computer system having architecture (1400), and specifically the core (1440) can provide functionality as a result of processor(s) (including CPUs, GPUs, FPGA, accelerators, and the like) executing software embodied in one or more tangible, computer-readable media. Such computer-readable media can be media associated with user-accessible mass storage as introduced above, as well as certain storage of the core (1440) that are of non-transitory nature, such as core-internal mass storage (1447) or ROM (1445). The software implementing various embodiments of the present disclosure can be stored in such devices and executed by core (1440). A computer-readable medium can include one or more memory devices or chips, according to particular needs. The software can cause the core (1440) and specifically the processors therein (including CPU, GPU, FPGA, and the like) to execute particular processes or particular parts of particular processes described herein, including defining data structures stored in RAM (1446) and modifying such data structures according to the processes defined by the software. In addition or as an alternative, the computer system can provide functionality as a result of logic hardwired or otherwise embodied in a circuit (for example: accelerator (1444)), which can operate in place of or together with software to execute particular processes or particular parts of particular processes described herein. Reference to software can encompass logic, and vice versa, where appropriate. Reference to a computer-readable media can encompass a circuit (such as an integrated circuit (IC)) storing software for execution, a circuit embodying logic for execution, or both, where appropriate. The present disclosure encompasses any suitable combination of hardware and software.

APPENDIX A: ACRONYMS

JEM: joint exploration model VVC: versatile video coding BMS: benchmark set

MV: Motion Vector HEVC: High Efficiency Video Coding

MPM: most probable mode

WAIP: Wide-Angle Intra Prediction SEI: Supplementary Enhancement Information VUI: Video Usability Information GOPs: Groups of Pictures TUs: Transform Units, PUs: Prediction Units CTUs: Coding Tree Units CTBs: Coding Tree Blocks PBs: Prediction Blocks HRD: Hypothetical Reference Decoder

SDR: standard dynamic range

SNR: Signal Noise Ratio CPUs: Central Processing Units GPUs: Graphics Processing Units CRT: Cathode Ray Tube LCD: Liquid-Crystal Display OLED: Organic Light-Emitting Diode CD: Compact Disc DVD: Digital Video Disc ROM: Read-Only Memory RAM: Random Access Memory ASIC: Application-Specific Integrated Circuit PLD: Programmable Logic Device LAN: Local Area Network

GSM: Global System for Mobile communications

LTE: Long-Term Evolution CANBus: Controller Area Network Bus USB: Universal Serial Bus PCI: Peripheral Component Interconnect FPGA: Field Programmable Gate Areas

SSD: solid-state drive

IC: Integrated Circuit CU: Coding Unit PDPC: Position Dependent Prediction Combination ISP: Intra Sub-Partitions SPS: Sequence Parameter Setting

While this disclosure has described several exemplary embodiments, there are alterations, permutations, and various substitute equivalents, which fall within the scope of the disclosure. It will thus be appreciated that those skilled in the art will be able to devise numerous systems and methods which, although not explicitly shown or described herein, embody the principles of the disclosure and are thus within the spirit and scope thereof. 

What is claimed is:
 1. A method for video decoding in a decoder, comprising: receiving coded information of pictures in a coded video sequence, the coded information including a coding tree unit (CTU) size information that indicates a CTU size selected for the pictures, the CTU size information being encoded using a truncated unary code; determining the selected CTU size based on the CTU size information encoded using the truncated unary code; and reconstructing samples in the pictures based on the selected CTU size.
 2. The method of claim 1, wherein the selected CTU size is 32×32, 64×64, or 128×128 luma samples.
 3. The method of claim 2, wherein the determining the selected CTU size comprises: determining, based on the CTU size information encoded using the truncated unary code, a coded value from a bit string in the coded information, a maximum number of bits in the bit string being 2, the coded value being 0, 1, and 2 when the bit string is 0, 10, and 11, respectively; and determining the selected CTU size based on the coded value.
 4. The method of claim 3, wherein the determining the selected CTU size comprises: determining that the selected CTU size is 128, 64, and 32 in a case that the coded value is 0, 1, and 2, respectively.
 5. The method of claim 4, wherein the determining that the selected CTU size is 128, 64, and 32 comprises: determining the selected CTU size to be 2^(CtbLog2SizeY), a value of CtbLog 2SizeY being a difference between 7 and the coded value.
 6. The method of claim 3, wherein the determining the selected CTU size comprises: determining that the selected CTU size is 32, 64, and 128 in a case that the coded value is 0, 1, and 2, respectively.
 7. The method of claim 6, wherein the determining that the selected CTU size is 32, 64, and 128 comprises: determining the selected CTU size to be 2^(CtbLog2SizeY) a value of CtbLog 2SizeY being a sum of the coded value and
 5. 8. The method of claim 1, wherein the coded information is in a sequence parameter set header for the coded video sequence.
 9. An apparatus for video decoding, comprising: processing circuitry configured to: receive coded information of pictures in a coded video sequence, the coded information including a coding tree unit (CTU) size information that indicates a CTU size selected for the pictures, the CTU size information being encoded using a truncated unary code; determining the selected CTU size based on the CTU size information encoded using the truncated unary code; and reconstruct samples in the pictures based on the selected CTU size.
 10. The apparatus of claim 9, wherein the selected CTU size is 32×32, 64×64, or 128×128 luma samples.
 11. The apparatus of claim 10, wherein the processing circuitry is configured to: determine, based on the CTU size information encoded using the truncated unary code, a coded value from a bit string in the coded information, a maximum number of bits in the bit string being 2, the coded value being 0, 1, and 2 when the bit string is 0, 10, and 11, respectively; and determine the selected CTU size based on the coded value.
 12. The apparatus of claim 11, wherein the processing circuitry is configured to: determine that the selected CTU size is 128, 64, and 32 in a case that the coded value is 0, 1, and 2, respectively.
 13. The apparatus of claim 12, wherein the processing circuitry is configured to: determine the selected CTU size to be 2^(CtbLog2SizeY) a value of CtbLog 2SizeY being a difference between 7 and the coded value
 14. The apparatus of claim 11, wherein the processing circuitry is configured to determine that the selected CTU size is 32, 64, and 128 in a case that the coded value is 0, 1, and 2, respectively.
 15. The apparatus of claim 14, wherein the processing circuitry is configured to: determine the selected CTU size to be 2^(CtbLog2SizeY) a value of CtbLog 2SizeY being a sum of the coded value and
 5. 16. The apparatus of claim 9, wherein the coded information is in a sequence parameter set header for the coded video sequence.
 17. A non-transitory computer-readable storage medium storing a program executable by at least one processor to perform: receiving coded information of pictures in a coded video sequence, the coded information including a coding tree unit (CTU) size information that indicates a CTU size selected for the pictures, the CTU size information being encoded using a truncated unary code; determining the selected CTU size based on the CTU size information encoded using the truncated unary code; and reconstructing samples in the pictures based on the selected CTU size.
 18. The non-transitory computer-readable storage medium of claim 17, wherein the selected CTU size is 32×32, 64×64, or 128×128 luma samples.
 19. The non-transitory computer-readable storage medium of claim 18, wherein the program is to perform: determining, based on the CTU size information encoded using the truncated unary code, a coded value from a bit string in the coded information, a maximum number of bits in the bit string being 2, the coded value being 0, 1, and 2 when the bit string is 0, 10, and 11, respectively; and determining the selected CTU size based on the coded value.
 20. The non-transitory computer-readable storage medium of claim 19, wherein the determining the selected CTU size comprises determining that the selected CTU size is 128, 64, and 32 in a case that the coded value is 0, 1, and 2, respectively. 